-Move /api/password-reset backend endpoint from authenticated router to unauthenticated router
-This fixes password reset at last
-Previously, trying to reset password throws HTTP Unauthorized error, but we can't expect user to be logged in (authenticated) when they forgot their password)

-Mark all existing password reset codes for the given user as used
-This prevents user from using old codes to reset password(potential security issue maybe?)

-Return a distinct HTTP response code to frontend when given password reset code has already been used
-This prevents a potential security issue when someone tries to reuse an existing password reset code

-Distinguish between different HTTP response codes returned from backend after sending password reset request
-Display descriptive error messages that match each known response code that backend would return
-Also provide a generic but user-friendly error message when an unknown HTTP response code for an error is returned from backend

-Align the CircleAlert icon vertically in the Alert component on the password reset page when error message is to be displayed

-Vertically align the CircleAlert icon in the center of the Alert component

-Fix the link that 'Reset password' clickable components on the frontend redirect to
-Now user is finally directed to the reset password page instead of a 404 Not Found page

-Make login errors slightly more distinguishable by returning distinct error codes in the HTTP response body depending on what issue ocurred while trying to verify the given username and password